Conversation
interim17
requested review from
ShrimpCryptid and
meganrm
and removed request for
a team
Coverage Report
File CoverageNo changed files found. |
meganrm
approved these changes
Feb 18, 2026
griffinfujioka
approved these changes
Feb 19, 2026
| - run: npm publish | ||
| env: | ||
| NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}} | ||
| - run: npm publish --provenance # Provenance required for Trusted Publishers |
Contributor
There was a problem hiding this comment.
Remember to update the package.json with the repository URL if it's not already in there
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our npm tokens are expired, and no one outside of infra was a maintainer anymore, preventing us from publishing a new version on npm.
We're taking this as an opportunity to move to using Trusted Publishing.
Infra says we should be set up on the NPM registry side, and this PR almost exactly mimics the comparable change in
vole-app:https://github.com/allen-cell-animated/vole-app/pull/475/files
I also mirrored the approach of pinning actions to particular commit hashes and bumped both versions on node and actions/setup-node.
I didn't downgrade actions/checkout but did use a hash for the version we were on.
I think to test this we will need to push a new version tag, I think the sequence will be to merge this first and then do a version release.